> Can you say a bit more about the rough edges you're encountering? 1) To avoid name mangling we had to write "rewrite style" for ever tag in the css file. 2) To avoid using a dedicated web server in tandem with Ur/Web, we had to inline a CSS file as a string and write a function that serves it as a blob 3) We had to declare every CSS tag inside the .ur file, duplicating what's in the css and the .urp file
For (1) it would be nice if there was a option to turn off all css name mangling in one command. For (2) and (3) it might be good if the compiler could take .css files as input and serve them itself, as well as processing them to extract all the tag names to save programmers typing them all out again. Once you know how to do it it's not much trouble so improving this stuff is not terribly important. On Mon, Jun 30, 2014 at 7:41 PM, Adam Chlipala <ad...@csail.mit.edu> wrote: > On 06/30/2014 02:08 PM, orchidaceae phalaenopsis wrote: >> >> Our app might be a bit simple but I thought it would >> be nice to release it publicly since we just reached our first big >> milestone: All the essential basic functionality is complete. We >> intend to polish it a bit and add some extra features but it already >> does everything we wanted. >> >> It's a little image gallery site which lets you upload pictures, tag >> them and then search by tags. Here is the source code: >> https://github.com/yuuko273/Gallury > > > Great, thanks! Do you have an application running at some public URL? > > >> * Dealing with CSS is really awkward! > > > Can you say a bit more about the rough edges you're encountering? > > > _______________________________________________ > Ur mailing list > Ur@impredicative.com > http://www.impredicative.com/cgi-bin/mailman/listinfo/ur _______________________________________________ Ur mailing list Ur@impredicative.com http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
