-
Notifications
You must be signed in to change notification settings - Fork 166
TODO for 1.0 #50
Comments
ping @afshin @blink1073 Add comments when you come across things which should be added to this list |
|
Hi folks -- can we get an update on the approximate timeline for 1.0? We are hoping to use Phosphor for a large UI project, and particularly need the ability to tear off (and return) windows from the docker. Thanks, |
Hello, I have same question. In next few months I will need to start working on huge desktop like application. Phosphor would help a lot on this. |
@vrmerlin @mladen107 I don't know the specific date for Maybe @sccolbert can fill you in on the projected timetable. |
I would agree from my experimentation that the library is very good as it is. I guess I'm asking because I particularly need the ability to tear off (and return) windows from the docker. My understanding is that that feature is still under development but planned for 1.0. |
@vrmerlin Are you talking about creating new browser windows? Or do you just mean tearing off tabs from a If you're talking about new windows (i.e., native browser windows), you're right that you cannot currently do that. But if you're talking about within a single window, the current version can support that. |
I'd like to be able to click a button on a docked panel and have it become it's own window on the screen. A button should be provided to allow it to be easily snapped back in. You can do this with Golden Layout: |
@vrmerlin Yep, that's in the plans. |
Will probably be available before |
That's great to hear, but I'm trying to understand if the feature is a few days or weeks away, or many months. I'm interested in a time frame so I can plan accordingly for our project, and let the review team know in our upcoming design review . |
greater than 1 month and less than many months (sorry that I can't be more specific) At the same time I add that functionality, I'll also the maximize-within-area functionality. |
Ok, thanks! On Aug 12, 2016 9:28 AM, "S. Chris Colbert" notifications@github.com wrote: 1 month and < many months (sorry that I can't be more specific) At the same time I add that functionality, I'll also the maximize-within-area functionality. You are receiving this because you were mentioned. |
Can we get an update on the progress and expected timeline towards 1.0? It's been 3 months since any code was modified. |
@vrmerlin I don't do big updates or changes on master, so be sure to check the other branches before drawing any conclusions as to activity ;) 1.0 should be ready soon. |
Oh, great, thanks! |
maximize and popup dock panels will be post 1.0. Closing this as complete modulo tests. |
🎉 |
Darn, I had the impression back in August that the pop-out panels were coming very soon. This was a very important feature to us. I'm thrilled to see that 1.0 is being finalized, but it's a big loss for us to not have that capability. |
@vrmerlin Don't worry, it's still coming as the next feature I work on. I'm just moving it to a feature release so other vested users can start updating their code. |
@sccolbert . First of all thank you very much for the great work. |
I think we decided on not making it a built-in feature of the DockPanel, but rather create a separate |
Does is make it possible to dock and un-dock the window to the DockPanel? |
It would yes. You can remove any widget from anything by moving it (programmatically) to a different parent widget. |
That's great. Looking forward to this feature. |
This is a list of things which need to be done before 1.0 release. Will add to list as I find things.
text
->label
where relevanttooltip
->caption
where relevantMaximize support for dock panelsTear out window support for dock panelscore/mimedata
dom/dragdrop
popAt
,remove
,removeAt
onActivateRequest
implementation for each widgetremoveTab
,removeItem
, etc.<a>
tags inside things like tabs, command items, and sidebar buttons.this
for sender type ofISignal
objects.vdom
.minSize >= maxSize
at all usage points.dispose
methods on layouts (some may be missing).readonly
.!important
for CSS hidden rules where appropriate.The text was updated successfully, but these errors were encountered: