On Mon, 4 Apr 2016 08:42:50 +0900 Carsten Haitzler (The Rasterman) <[email protected]> wrote:
> On Sun, 03 Apr 2016 17:37:16 +0300 Yakov Goldberg > <[email protected]> said: > > > Tom, Raster thanks for comments. > > > > Wiki: https://phab.enlightenment.org/w/ui_builders_format/ > > Changes: > > - first letter of widget is now lower case; > > - fixed indentation - 4 spaces everywhere; > > - fix Resource description; > > - other minor updates. > > > > The reason I put resources separately is that I was still thinking > > in Erigo scope. > > You are right - resources should be right in the text. > > And then gui builders should be able use API to get list of > > resources, so GUI_BLDR'S own project files can be created to handle > > resource aliases. As for format I like: > > > > res("path/layout.edj") > > or > > @"path/layout.edj" > > or > > ₪"path/layout.edj" > > :) > > ...can be decided a little bit later > > well i started work on this being done at runtime with "magic file > paths" in efl. so far i have: > > "/path/to/whatever" <- normal > "./path/to/whatveer" <- normal > "../path/to/whatever" <- normal > "path/to/whatever" <- normal (same as ./path/to/wahtever) > > and new ones: > > "~/path/to/whatever" <- like in shell > "~username/path/to/whatever" <- like in shell > "@key/path/to/whatever" <- new "magic location" where key is set at > runtime > > so it's buried inside the path string itself. what they keys are will > work out over time. i'm starting with some basics: > > @home <- same as ~/ > @tmp <- /tmp (or TMPDIR or other env vars pointing to where tmp > should be) @data <- XDG_DATA_HOME = ~/.local/share > @config <- XDG_CONFIG_HOME = ~/.config > @cache <- XDG_CACHE_HOME = ~/.cache > @run <- XDG_RUNTIME_DUR - depends likely set to /var/run/user/UID > > also likely: > > @download <- ~/Download > @desktop <- ~/Desktop > @documents <- ~/Documents > @music <- ~/Music > @pictures <- ~/Pictures > @templates <- ~/.Templates > @videos <- ~/Videos > > i am THINKING of app specific keys like: > > @app.dir/ (prefix) > @app.bin/ (prefix/bin) > @app.lib/ (prefix/lib) > @app.data/ (prefix/share/appname) > @app.locale/ (prefix/share/locale) > @app.config/ (@config/appname) > @app.cache/ (@cache/appname) > @app.local/ (@data/appname) > > ... maybe some more. then we get to the problem that efl itself > should use this too so i think over time efl should centralize data > in PREFIX/share/efl (and binaries, libraries etc. go int he same dir > anyway due to efl building as a single unit) so i am expecting to > have: > > @efl.dir/ > @efl.bin/ > @efl.lib/ > @efl.data/ > @efl.locale/ > @efl.config/ > @efl.cache/ > @efl.locale/ > > ... > > the same code CAN in theory do: > > file:/// ..... (but i have to write a uri parser/converter first) > http://.... (but then i have to write a whole http fetcher, > downloader, cacher) > ssh://.... (like with http - but need to use > libssh etc.) As part of my SledjHamr project, I'm looking at http caching now. Polipo is something I have been using for some time as a web cache / proxy / filter. I feel it's a good match for my big virtual world project. I'm thinking it might port easily to EFL, which I'm likely to do eventually. It cleans up client and server side protocols, promoting them to the latest and the fastest. Includes SOCKS4 / 5 for upstream, which I have been using via ssh. Was designed to be a single user (mostly) proxy, which fits my needs at least. It even has a filter which I feed converted AdBlock+ filter files to. Since it cleans up protocols as a proxy layer, I figure it's fetcher and server bits might be usable anywhere I need an HTTP fetcher or server. SledjHamr relies a lot on HTTP to shift assets around, so that will be useful to me. Even file:// will be useful, one of my major features is that SledjHamr defaults to running a local server on your desktop hard drive. I had previously ported luaproc to EFL, and I expect similar results if I port polipo, lots of the code vanished, since it was just implementing stuff EFL does anyway. Which is what makes such things good candidates for EFL porting. B-) I've not been commenting on the UI syntax, since I've been working on my own, which is a C / Lua reboot of something I wrote long ago in Java. It's designed to suit my needs. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
