- User Since
- Jul 6 2021, 16:29 (15 w, 1 d)
Sun, Oct 17
Sat, Oct 16
Also this Vagrant pattern should work first-run: https://we.phorge.it/T15027#852
Tue, Oct 5
We cam have a i18n option for both confirmDialog and alertDialog.... Let's do this, who is down?
Thanks -- Can anyone think of a more generic solution here as far as dialogs? Something for both confirm() and prompt().
Sep 17 2021
What if, to get this functionality pushed through, we for now change the verbiage to two English words -- "Discard changes?"
Sep 13 2021
Dug up some more info as well...
Sep 4 2021
Aug 24 2021
Does anyone like, not like, or have additional thoughts on the general idea of making one or more unique identifiers that isn't "phorge", for the purpose of an identifier that is unmistakably greppable? I outlined some notes on this idea here: T15006#831
Aug 19 2021
Also I don’t believe javelin.io is related to the Javalin used in Phab.
Oh, another potential concern...
Jul 28 2021
I 100% agree with this. Is there no way to invoke internationalization via JS only? If not, that's perfectly great, but wondering about an answer offhand.
Jul 26 2021
I would like to be a part of the core team, and I've signed the document.
Jul 25 2021
On a related note, tonight I discovered this UIExamples application (changing links from my Vagrant install):
Would it be easy to change the prompt to be more descriptive with actions?
For me, I think it might be on the hard side... and maybe add some bloat? Unless there is a styled generic confirm box created that maybe uses a callback instead of blocks execution...
Jul 24 2021
Jul 18 2021
Jul 16 2021
Jul 13 2021
Found that SVN works great for a monorepo... Does Mercurial as well?
Confirmed working fine in both Windows 10 and Linux Mint 20
Jul 7 2021
Here is a proof-of-concept for a Vagrant pattern.
Actually here is where that particular library is registered: https://we.phorge.it/source/phorge/browse/master/src/__phutil_library_init__.php$3
Jul 6 2021
Added related task T15006 since it could likely serve as a reference for this one... Please undo or stop me if I'm overstepping boundaries
I want to also mention on this topic... Using a pre-packaged VirtualBox image can be a straightforward distribution route, with a drawback being filesize... Perhaps Torrents could be a neat way alternative to distribute something like that, though there would be a few options including sponsored mirrors, etc... VirtualBox is a common Vagrant provider, so oftentimes it is a prerequisite anyway...
We should consider a Vagrantfile
For projects that were tracking upstream previously and able to merge, would this not be a matter of a Git config update to add or swap remotes then merge?