Images/wiki imgs dir #652
Images/wiki imgs dir #652
Conversation
Cleaned up from the pdf, alpha and optimized pngs. Can be used for wiki page also.
For a "Micro"soft Python (Windows) wiki page for tweaks and other OS specific stuff.
micro.ico: has 16px - 128px bundled images. This is the full multipurpose desktop ico micro48.ico: has just 48px size optimized to fit on the pyboard micro48.png: The optimized png made from vector-logo-3.png The Autorun.inf customization contents just for reference in commit log also. [Autorun] Icon=micro48.ico Label=Micro Python
These certainly should not live in the source code repository. For hardware stuff, there's separate https://github.com/micropython/pyboard which already has images of the board. So, if these images are solely for wiki usage, it should be hosted elsewhere. Ideally, uploaded into wiki, if it supports that, otherwise, hosted on some server. (Ab)using a git repo to host them would be last choice, and then, it should be a separate repo (so if hosting provider had problems with terms of service compliance for such repo, it killed only it ;-) (just kidding)). |
|
Umm, Ok that a bit more understandable, a separate resources repo be better for hosting some of the "other stuff" like images for wiki linking/etc. These are for general other stuff. I can't make a separate repo, so what would be the best route for stuff like this, so that stuff doesn't get broken(links, etc...) in the future. I'm guessing a "resources/other/misc" named repo maybe. |
|
You can create a repo in your account and use that. Once you do maintenance on it and wiki for some reasonable time (e.g. couple of months), it would make sense to talk about transferring it to main account. Otherwise we can end up with bunch of random unmaintained stuff which yet looks like a part of project (and thus leaves mixed impression). |
|
I guess that is an option also... Also could the pyboard repo get some actual pics of the shipped v1.0 board top/bottom please. There are no loose pngs(I photoshop extracted them, then optimized em from the pdf), and where is the 3D model used? |
|
Has anyone checked out this. It says each user/organization can have 1 website hosted. It would be perfect for a community type of site everyone can help out with, with various stuff, such as a "wiki" style site. |
That looks cool, but we already have wiki.micropython.org that anyone can edit (as well as the github dev wiki, the forum, and the official micropython.org docs...). I don't want to dilute further the web resources, because then people get confused, and information become stale quickly. |
Can you please open separate ticket for these (each), probably in https://github.com/micropython/pyboard , otherwise it's hard to track outstanding issues. (And I guess it may take some time for @dpgeorge to get to these.) |
|
Ok, I made a couple issues on the other repo regarding this one. |
|
Thanks for the images, but, as @pfalcon says, this repo is not the right place for them. I added an images/ directory to the pyboard repo (and put some photos there), and can add the relvant images from this PR to that directory. |
|
Renders of the pyboard added to the micropython/pyboard repo. We'll need to find a place for the other pics... |
QSPI is not currently working so its commented out. This is progress on micropython#652.
This evolves the API from 2.x (and breaks it). Playback devices are now separate from the samples themselves. This allows for greater playback flexibility. Two sample sources are audioio.RawSample and audioio.WaveFile. They can both be mono or stereo. They can be output to audioio.AudioOut or audiobusio.I2SOut. Internally, the dma tracking has changed from a TC counting block transfers to an interrupt generated by the block event sent to the EVSYS. This reduces the overhead of each DMA transfer so multiple can occure without using up TCs. Fixes micropython#652. Fixes micropython#522. Huge progress on micropython#263
Images dir for wiki/mindmap/3D/etc usage.