Yes, we can continue specifics on github, or in gmail or wherever. However -- I think that if you have a standalone skin or recipe, and you feel it it mature enough, put up a page for it on the wiki. It's tought keeping all the documentation up-to-date, but generally pmwiki.org serves as the central clearing-house for pmwiki-related things. The more resources that are available, the more active projects are seen, all the better!
IMHO. -Michael Paulukonis http://www.xradiograph.com <http://goog_2112721603>Interference Patterns (a blog)<http://www.xradiograph.com%5Cinterference> @XraysMonaLisa <https://twitter.com/XraysMonaLisa> http://michaelpaulukonis.com <http://www.BestAndroidResources.com> Sent from somewhere in the Cloud (hearthrug, by the fender) On Tue, Jun 18, 2013 at 10:18 PM, Tamara Temple <[email protected]>wrote: > michael paulukonis <[email protected]> wrote: > > Tamara -- I hope that I've made the TwitterBootstrap - > http://www.pmwiki.org/wiki/Skins/TwitterBootstrap - a standalone skin. > That's the goal, > > anyway. > > I think you are there, but I wasn't entirely sure it was ready for use? > It may be that I'm wrong, but it still looked like there was some work > to be done? If not, my apologies. > > > I have added markup to handle some bootstrap features, and added some > configuration options like I've seen in other skins. It has some > > work to be done to it, certainly. > > I would love to see more PmWiki Markup around this. I was building out > some of my pages to use bootstrap features, and it was getting a bit > verbose and painful, so I'd really like to see some work there. > > > However, there is certainly room for more than one Skin. I've kept the > name pretty generic, which may have been a mistake. > > Please feel free to start up a standalone page for it, as well. > > There is -- I did reply to the issue you raised in my repo -- I really > should have said something to you in yours as well; my apologies (it was > just a wild hair I got Sunday morning!) > > I think there is a possibility to converge, but I do see we have taken > different approaches to skinning, which we should discuss before any > merging takes place. > > As for a separate skin page -- hmm, I think I could do that; but I'd > like to keep them harmonized as well. Petko, PM, others who've been > talking about skins, what do you think? I'm flexible, either way. > > > > My pmwiki messages are being buried by gmail, so I haven't been very > active on the mailing lists. :-( > > No worries, here. You and I can certainly continue this specific > discussion in github? > > > -Michael Paulukonis > > http://www.xradiograph.com > > Interference Patterns (a blog) > > @XraysMonaLisa > > http://michaelpaulukonis.com > > > > Sent from somewhere in the Cloud > > (hearthrug, by the fender) > > > > On Sun, Jun 16, 2013 at 3:41 PM, Tamara Temple <[email protected]> > wrote: > > > > I know Michael Paulukonis is working on one of these, but I decided > to > > just go ahead and throw one together. I think Michael is working on > > pulling apart the TwitterBootstrap recipe, which is far more than > just a > > skin. This is my implementation of the skin, following the pattern I > set > > in MouseSkin and borrowed from others, of using wiki pages to define > > most of the content of the page areas, but still utilizing the > bootstrap > > markup. > > > > * Github: https://github.com/tamouse/pmwiki-bootstrap-skin > > * Working site: http://wiki.tamaratemple.com/ > > > > I'm sort of reluctant to just throw my version up on the Skins group > > since Michael has staked that area out. I've added a link to the > > Skins/TwitterBootstrap-Talk page instead. > > > > _______________________________________________ > > pmwiki-users mailing list > > [email protected] > > http://www.pmichaud.com/mailman/listinfo/pmwiki-users > > >
_______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
