Hi there,

I'm writing a plugin recently to implement a app-like mobile display, which 
is available here: https://trac-hacks.org/wiki/TracMobilePlugin

In my point of view, responsive framework requires lots of efforts in 
refactoring and debugging, and not achieving the best effect: you know, the 
concept of designing UI is different on PC and mobile, as PC is good at 
displaying tables, while mobile is good at display lists, etc.

By the way: writing a vuejs based mobile app is surprisingly easy, 
TracMobilePlugin is supporting nearly all main features of trac except 
milestones and source repo, in only one week: faster than I ever excepted, 
as I'm actually a starter in vuejs.

On Tuesday, January 23, 2018 at 5:22:43 AM UTC+8, RjOllos wrote:
> On Tuesday, January 16, 2018 at 6:00:35 PM UTC, hire...@gmail.com 
> <javascript:> wrote:
>> On Friday, January 12, 2018 at 3:44:23 PM UTC-6, RjOllos wrote:
>>> Just to repeat here what was said in #11953, rather than creating a 
>>> branch you'll be better off writing a theme for Trac. ...
>> Thanks for pointing us toward those resources. I hadn't considered the 
>> theming plug-ins previously, as I hadn't envisioned the look & branding 
>> aspects as something I would need to change very often once they're set up. 
>> I can see where defining some instance wide variables and then passing them 
>> to theme class instances could address some of what I'm struggling with 
>> though. 
>> Trac 1.4 is pretty much finished up...
>>> - Ryan
>> I'm happy to hear this, but also somewhat confused. Looking at open 
>> tickets, dates, etc. for nex-dev1.3.x and 1.4 milestones, the impression I 
>> got was of a project that has a lot of outstanding work to do before 
>> hitting those milestones, and many decisions about things like multiple 
>> projects still to be made. I'm happy to have been mistaken about that, and 
>> am grateful for the work folks have done to get within striking distance of 
>> a new stable reference release. 
> The tickets in next-dev-1.3.x are unscheduled and probably won't be 
> completed for 1.4. The milestone will be renamed next-dev-1.5.x at that 
> time.
>> Would would you perhaps be willing to give an update on which of the many 
>> tickets & proposals that have been floated are "IN" for the 1.4 release 
>> (and thus a high-priority for attention) and which are being put aside for 
>> future consideration? The most recent post to this group about it suggested 
>> 1.3.3 was to close last August with 1.4 release candidates to follow 
>> thereafter. I'm not saying this to be critical about missing dates, this is 
>> a community-project after all. Rather, I wan't to get a handle on which of 
>> the many different pieces of the puzzle are most relevant going forward.
> The tickets in 1.3.3 and 1.4 will likely get resolved for the respective 
> releases. I haven't had much time the past 3 months to move forward with 
> the release.
> We've discussed adding a preprocessor like Less or Sass, and it seems 
> worthwhile. There is some discussion in #10672 about adding a preprocessor. 
> I've been wanting to move that ticket to completion. If that's something 
> you'd like to work on, we'd welcome the contribution.
> https://trac.edgewall.org/ticket/10672
> If there a refactorings of the CSS on the trunk that can help with 
> implementing themes, we'd also welcome those contributions. You can fork 
> the project on GitHub and propose changes (though we don't directly merge 
> pull requests, we can merge from your forked branch). Please be sure to 
> make your changes atomic for review and to ease rebasing.
> https://trac.edgewall.org/wiki/TracDev/SubmittingPatches#MultipleChangesets
> - Ryan

You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to